![]() |
![]() |
![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
![]() |
To access the contents, click the chapter and section titles.
Oracle Performance Tuning and Optimization
Part III
|
Chapter | 16 | OLTP System |
17 | Batch Processing System | |
18 | Decision Support System | |
19 | Data Warehousing System | |
20 | BLOB System | |
21 | The Oracle Parallel Server System | |
22 | Optimal Backup and Recovery | |
23 | Miscellaneous Configurations |
Part II of this book explained how to tune the database server: the RDBMS itself as well as the server operating system. It also explored the computer hardware and touched on some of the ways you can configure the server itself to take advantage of specific data access patterns.
Part III of this book looks at specialized configurations based on those data patterns. The following chapters detail several different types of systems ranging from traditional OLTP and decision support systems to some of the newer data warehousing and BLOB systems. The chapters analyze the systems and determine the data access patterns of these types of applications. After characterizing the system, you look at some design considerations that most effectively take advantage of that knowledge. Finally, you will look at some of the ways the RDBMS and server operating system can be tuned to perform optimally in the particular type of configuration.
By understanding and characterizing the data access patterns on your system and understanding the characteristics of Oracle, your server OS, and hardware, you can effectively design an optimal system. Not all systems are alike and not all the things discussed in these chapters will apply directly to your system. Although each system is unique, the concepts will provide some useful insight about how you can optimize your own system.
Probably the most common type of RDBMS system in use today is the OnLine Transaction Processing (OLTP) system. Almost everyone has some interaction with an OLTP system every day, whether they realize it or not. OLTP systems are used in grocery stores to keep track of items that have been sold and that must be restocked. OLTP systems are used in banks to keep track of savings and checking accounts. OLTP systems are used to keep track of how much money you charged to your credit card and to send you a bill each month. OLTP systems are used in the airline industry to keep track of schedules and seats sold on airplanes. In fact, every aspect of our lives is probably touched by some type of OLTP system.
This chapter looks at the OLTP system and analyzes the characteristics of the system and the data access patterns typically involved with the OLTP system. Having analyzed the system, you can then look at some of the ways you can optimally design and tune the system. Finally, you determine whether some enhancements can be made to the RDBMS, OS, or hardware to improve system performance.
The OLTP system usually involves many users, each of whom accesses the system randomly by using various types of transactions. Although some OLTP systems use only one type of transaction at a time, most OLTP systems have many different types of transactions happening simultaneously. Whether one or many different types of transactions occur, the general characteristics of the OLTP system are the same:
Each of these characteristics requires special configuration considerations, as you see later in this chapter. The load and response time requirements, as well as the number of users to be supported, are all factors in the type and size of the computer used to meet those requirements.
Previous | Table of Contents | Next |
![]() |
Products | Contact Us | About Us | Privacy | Ad Info | Home
Use of this site is subject to certain Terms & Conditions, Copyright © 1996-2000 EarthWeb Inc. All rights reserved. Reproduction whole or in part in any form or medium without express written permission of EarthWeb is prohibited. |